Tag Management
A tag is a uniquely identified position in a network (plant/facility) performing a specific function through a specific item at a point in time. AssetWise lets you manage both what can be used in a specific tag position and what is currently fitted in the tag position.
AssetWise uses three objects to manage assets within a system:
- Tags - Functional location. Informally, a tag is sometimes referred to as the hole in the ground and its associated requirements.
- Physical Items - Tags always exist in the context of a larger system (primary physical item).
- Serial Items - When you implement the design, the tag moves into the physical world where all you have is serial items (physical tangible things). You can only fit a serial item into another parent serial item.
To use a simple example, suppose you are renovating a kitchen, and you are installing a new refrigerator.
- The tag is the space in the kitchen designated for the refrigerator.
- The physical item is the make and model of the refrigerator you ordered.
- The serial item is the actual refrigerator that gets delivered and installed.
The following image shows the relationships between tags, physical items, and serial items in a managed environment. The left-hand side of the image represents the design view (paper view), and the right-hand side of the image represents the physical world (As-built view).
Tag Identification
Tags must be uniquely identified within the system and they must have a specific function; otherwise, it's difficult to manage within the system. For a tag, you want to be able to control changes and conduct audits to see what changes were done over a period of time. You also want to know what equipment was removed or fitted in the tag over a period of time, what is the tag's current status, and has it been approved for use.
A tag is identified by the following properties:
- Tag Number (Code in AssetWise Director) and Revision - Tags require a unique code and an optional revision number.
- Primary Physical Item / Unit - Tags always exist in the context of a larger system (parent physical item). In a Nuclear Plant, the primary physical item / unit is usually a plant or facility. In the case of a memory slot in a computer, the primary physical item / unit is the computer.
- Function / System - The system is the functional requirements for the tag. For example, if the tag is a DVD drive in a computer, the function / system for the DVD drive is probably the External Peripherals system, which is represented in AssetWise by grouped virtual items.
- Classification - Tags require a class that must be created prior to tag creation.
Tag Design View
Tags always exist in the context of a larger system. For example, in a Nuclear Plant you may have two tags that represent different pipelines. These tags (pipelines) then exist in the context of the Nuclear Plant, or the primary physical item. The image below shows two empty tags in the context of the Nuclear Plant.
When the physical item (equipment) is installed in the tag position, it can perform work. The following image shows the physical items fitted into the tag positions. These images represent tags in the design world, or on a drawing.
Tag As-built View
When you go out to the field and implement the design, the tag moves into the physical world and you fit a serial item into the tag position to do the physical work. The image below represents the tags with the fitted serial items (As-built view).
Tag Pre-requisites
To adequately define tags in AssetWise, additional attributes and lookup table values must be defined beforehand. The following tasks are recommended:
- Define a classification structure with related user-defined attributes (item characteristics)
- Define a list of Units of Measure (System Admin > Maintain List Values > Units of Measure)
- Define Alternative Numbering Categories (System Admin > Maintain List Values > Alternative Numbering Categories) if you are using alternative names for tags. For more information, see Alternative Names Topic.
- Define both the Parent Physical Item and the Installed Physical Items for the tag.
- Define both the Parent Serial Item and the Fitted Serial Items that will be fitted into the parent serial item via the tag.
Refer to the AssetWise Administration Guide for details on Maintain List values tables. If a System generated physical item number is required, an appropriate numbering mask must be defined in the System Defaults.